System and method for generating embeddable widgets which enable access to a cloud-based collaboration platform

ABSTRACT

Techniques are disclosed for generating embeddable widgets capable of accessing contents in a cloud-based platform. In one embodiment, a method comprises receiving a request identifying a target content in the cloud-based platform. The method further comprises automatically generating a plurality of software codes which correspond to a software widget that enables access to the target content. According to some embodiments, the software widget is to be embedded in a software product so as to enable a user of the software product to access the target content without navigating away from the software product. Among other advantages, embodiments disclosed herein provide easy integration of centralized contents to users and third-party web-service vendors, and reduce the effort necessary for system administrators in controlling data security and tracking different activities performed to the centralized content, thereby enabling more intuitive user experience without sacrificing data security.

CROSS-REFERENCE TO RELATED APPLICATIONS AND EFFECTIVE FILING DATE ENTITLEMENT

This application is entitled to the benefit of and the right of priority to U.S. Provisional Patent Application No. 61/710,182, entitled “EMBEDDED HTML FOLDER WIDGET FOR ACCESSING A CLOUD COLLABORATION PLATFORM AND CONTENT FROM ANY SITE” (Attorney Docket No. 61599-8065.US00), filed Oct. 5, 2012, which is hereby incorporated by reference in its entirety. This application is therefore entitled to an effective filing date of Oct. 5, 2012.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the United States Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever. The following notice applies to the software and data as described below and in the drawings that form a part of this document: Copyright 2013, Box, Inc., All Rights Reserved.

BACKGROUND

With the advancements in digital technologies, data proliferation and the ever increasing mobility of user platforms have created enormous amounts of information traffic over mobile and computer networks. This is particularly relevant to the increase of electronic and digital contents being used and shared over the network in social settings and working environments as compared to traditional stand-alone personal computers and mobile devices. As a result, contents are shared across multiple devices among multiple users.

Moreover, the concept of cloud computing has changed many ways how data are stored and shared. Webpages now can provide much richer functionalities than their predecessors which may only be able to convey text-based information. Thus, the traditional boundaries separating software applications, data storage, and web-based services gradually become obscure. However, there is still a need for improved ways that can provide better integration and more intuitive user experience without sacrificing data security.

BRIEF DESCRIPTION OF DRAWINGS

The present embodiments are illustrated by way of example and are not intended to be limited by the figures of the accompanying drawings. In the drawings:

FIG. 1 depicts an example diagram of a system having a host server of a cloud service, collaboration and/or cloud storage accounts with capabilities that generate embeddable widgets capable of accessing contents in a cloud-based platform;

FIG. 2 depicts an example diagram of a web-based or online collaboration platform deployed in an enterprise or other organizational setting for organizing work items and workspaces;

FIG. 3 depicts an example diagram of a workspace in an online or web-based collaboration environment accessible by multiple collaborators through various devices;

FIG. 4 depicts a block diagram illustrating an example of components in a host server with capabilities that generate embeddable widgets capable of accessing contents in a cloud-based platform;

FIG. 5A-5C respectively depict screenshots showing example user interfaces embodying one or more techniques disclosed herein for generating embeddable widgets capable of accessing a file in a cloud-based platform;

FIG. 6A-6C respectively depict screenshots showing example user interfaces embodying one or more techniques disclosed herein for generating embeddable widgets capable of accessing a folder in a cloud-based platform;

FIG. 7 depicts a flowchart illustrating an example process for generating embeddable widgets capable of accessing contents in a cloud-based platform; and

FIG. 8 depicts a diagrammatic representation of a machine in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, can be executed.

The same reference numbers and any acronyms identify elements or acts with the same or similar structure or functionality throughout the drawings and specification for ease of understanding and convenience.

DETAILED DESCRIPTION

Techniques are disclosed for generating embeddable widgets capable of accessing contents in a cloud-based platform. In one embodiment, a method comprises receiving a request identifying a target content in the cloud-based platform. The method further comprises automatically generating a plurality of software codes which correspond to a software widget that enables access to the target content. According to some embodiments, the software widget is to be embedded in a software product so as to enable a user of the software product to access the target content without navigating away from the software product.

Among other advantages, embodiments disclosed herein provide easy integration of centralized contents to users and third-party web-service vendors, and reduce the effort necessary for system administrators in controlling data security and tracking different activities performed to the centralized content, thereby enabling more intuitive user experience without sacrificing data security.

The following description and drawings are illustrative and are not to be construed as limiting. Numerous specific details are described to provide a thorough understanding of the disclosure. However, in certain instances, well-known or conventional details are not described in order to avoid obscuring the description. References to one or an embodiment in the present disclosure can be, but not necessarily are, references to the same embodiment; and, such references mean at least one of the embodiments.

Reference in this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which can be exhibited by some embodiments and not by others. Similarly, various requirements are described which can be requirements for some embodiments but not other embodiments.

The terms used in this specification generally have their ordinary meanings in the art, within the context of the disclosure, and in the specific context where each term is used. Certain terms that are used to describe the disclosure are discussed below, or elsewhere in the specification, to provide additional guidance to the practitioner regarding the description of the disclosure. For convenience, certain terms can be highlighted, for example using italics and/or quotation marks. The use of highlighting has no influence on the scope and meaning of a term; the scope and meaning of a term is the same, in the same context, whether or not it is highlighted. It will be appreciated that same thing can be said in more than one way.

Consequently, alternative language and synonyms can be used for any one or more of the terms discussed herein, nor is any special significance to be placed upon whether or not a term is elaborated or discussed herein. Synonyms for certain terms are provided. A recital of one or more synonyms does not exclude the use of other synonyms. The use of examples anywhere in this specification including examples of any terms discussed herein is illustrative only, and is not intended to further limit the scope and meaning of the disclosure or of any exemplified term. Likewise, the disclosure is not limited to various embodiments given in this specification.

Without intent to limit the scope of the disclosure, examples of instruments, apparatus, methods and their related results according to the embodiments of the present disclosure are given below. Note that titles or subtitles can be used in the examples for convenience of a reader, which in no way should limit the scope of the disclosure. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. In the case of conflict, the present document, including definitions will control.

FIG. 1 illustrates an example diagram of a system 100 having a host server 110 of a cloud service/platform, collaboration and/or cloud storage service with capabilities that that generate embeddable widgets capable of accessing contents in a cloud-based platform.

The client devices 102 can be any system and/or device, and/or any combination of devices/systems that is able to establish a connection, including wired, wireless, cellular connections with another device, a server and/or other systems such as host server 110 and/or a third-party application 120. Client devices 102 typically include a display and/or other output functionalities to present information and data exchanged between/among the devices 102, the third-party application 120, and/or the host server 110.

For example, the client devices 102 can include mobile, hand held or portable devices or non-portable devices and can be any of, but not limited to, a server desktop, a desktop computer, a computer cluster, or portable devices including, a notebook, a laptop computer, a handheld computer, a palmtop computer, a mobile phone, a cell phone, a PDA, a smart phone (e.g., a BlackBerry device such as BlackBerry Z10/Q10, an iPhone, Nexus 4, etc.), a Treo, a handheld tablet (e.g. an iPad, iPad Mini, a Galaxy Note, Galaxy Note II, Xoom Tablet, Microsoft Surface, Blackberry PlayBook, Nexus 7, 10 etc.), a phablet (e.g., HTC Droid DNA, etc.), a tablet PC, a thin-client, a hand held console, a hand held gaming device or console (e.g., XBOX live, Nintendo DS, Sony PlayStation Portable, etc.), iOS powered watch, Google Glass, a Chromebook and/or any other portable, mobile, hand held devices, etc. running on any platform or any operating system (e.g., Mac-based OS (OS X, iOS, etc.), Windows-based OS (Windows Mobile, Windows 7, Windows 8, etc.), Android, Blackberry OS, Embedded Linux platforms, Palm OS, Symbian platform, Google Chrome OS, and the like. In one embodiment, the client devices 102, and host server 110 are coupled via a network 106. In some embodiments, the devices 102 and host server 110 can be directly connected to one another.

The input mechanism on client devices 102 can include touch screen keypad (including single touch, multi-touch, gesture sensing in 2D or 3D, etc.), a physical keypad, a mouse, a pointer, a track pad, motion detector (e.g., including 1-axis, 2-axis, 3-axis accelerometer, etc.), a light sensor, capacitance sensor, resistance sensor, temperature sensor, proximity sensor, a piezoelectric device, device orientation detector (e.g., electronic compass, tilt sensor, rotation sensor, gyroscope, accelerometer), or a combination of the above.

Signals received or detected indicating user activity at client devices 102 through one or more of the above input mechanism, or others, can be used by various users or collaborators (e.g., collaborators 108) for accessing, through network 106, a web-based collaboration environment or online collaboration platform (e.g., hosted by the host server 110). The collaboration environment or platform can have one or more collective settings 105 for an enterprise or an organization that the users belong, and can provide an user interface 104 (e.g., via a webpage application accessible by the web browsers of devices 102) for the users to access such platform under the settings 105. Additionally, a client software that is native to the cloud collaboration platform can be provided (e.g., through downloading from the host server 110 via the network 106) to run on the client devices 102 to provide cloud-based platform access functionalities. The users and/or collaborators can access the collaboration platform via a client software user interface 107, which can be provided by the execution of the client software on the devices 102.

The collaboration platform or environment hosts workspaces with work items that one or more users can access (e.g., view, edit, update, revise, comment, download, preview, tag, or otherwise manipulate, etc.). A work item can generally include any type of digital or electronic content that can be viewed or accessed via an electronic device (e.g., device 102). The digital content can include .pdf files, .doc, slides (e.g., Powerpoint slides), images, audio files, multimedia content, web pages, blogs, etc. A workspace can generally refer to any grouping of a set of digital content in the collaboration platform. The grouping can be created, identified, or specified by a user or through other means. This user can be a creator user or administrative user, for example.

In general, a workspace can be associated with a set of users or collaborators (e.g., collaborators 108) which have access to the content included therein. The levels of access (e.g., based on permissions or rules) of each user or collaborator to access the content in a given workspace can be the same or can vary among the users. Each user can have their own set of access rights to every piece of content in the workspace, or each user can be different access rights to different pieces of content. Access rights can be specified by a user associated with a workspace and/or a user who created/uploaded a particular piece of content to the workspace, or any other designated user or collaborator.

In general, the collaboration platform allows multiple users or collaborators to access or collaborate efforts on work items such each user can see, remotely, edits, revisions, comments, or annotations being made to specific work items through their own user devices. For example, a user can upload a document to a workspace for other users to access (e.g., for viewing, editing, commenting, signing-off, or otherwise manipulating). The user can login to the online platform and upload the document (or any other type of work item) to an existing workspace or to a new workspace. The document can be shared with existing users or collaborators in a workspace.

In general, network 106, over which the client devices 102 and the host server 110 communicate can be a cellular network, a telephonic network, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet, or any combination or variation thereof. For example, the Internet can provide file transfer, remote log in, email, news, RSS, cloud-based services, instant messaging, visual voicemail, push mail, VoIP, and other services through any known or convenient protocol, such as, but is not limited to the TCP/IP protocol, Open System Interconnections (OSI), FTP, UPnP, iSCSI, NSF, ISDN, PDH, RS-232, SDH, SONET, etc.

The network 106 can be any collection of distinct networks operating wholly or partially in conjunction to provide connectivity to the client devices 102 and the host server 110 and can appear as one or more networks to the serviced systems and devices. In one embodiment, communications to and from the client devices 102 can be achieved by, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet. In one embodiment, communications can be achieved by a secure communications protocol, such as secure sockets layer (SSL), or transport layer security (TLS).

In addition, communications can be achieved via one or more networks, such as, but are not limited to, one or more of WiMax, a Local Area Network (LAN), Wireless Local Area Network (WLAN), a Personal area network (PAN), a Campus area network (CAN), a Metropolitan area network (MAN), a Wide area network (WAN), a Wireless wide area network (WWAN), enabled with technologies such as, by way of example, Global System for Mobile Communications (GSM), Personal Communications Service (PCS), Digital Advanced Mobile Phone Service (D-Amps), Bluetooth, Wi-Fi, Fixed Wireless Data, 2G, 2.5G, 3G, 4G, IMT-Advanced, pre-4G, 3G LTE, 3GPP LTE, LTE Advanced, mobile WiMax, WiMax 2, WirelessMAN-Advanced networks, enhanced data rates for GSM evolution (EDGE), General packet radio service (GPRS), enhanced GPRS, iBurst, UMTS, HSPDA, HSUPA, HSPA, UMTS-TDD, 1xRTT, EV-DO, messaging protocols such as, TCP/IP, SMS, MMS, extensible messaging and presence protocol (XMPP), real time messaging protocol (RTMP), instant messaging and presence protocol (IMPP), instant messaging, USSD, IRC, or any other wireless data networks or messaging protocols.

Third-party applications 120 may be provided by third-party software application vendors and may be accessible to the users via the network 106. For example, third-party applications 120 can be provided through webpages provided from servers hosted by the third-party software application vendors using the Internet; for another example, third-party applications 120 can be provided using webpages that are operated by a server serving an intranet (e.g., within a corporate setting). Additionally, third-party applications 120 can also be provided via, after download (and installation if required), software codes (e.g., applications) running on the user devices 102. In any of the above configurations, the third-party applications 120 may communicate with the host server 110 for accessing cloud-based collaboration platform, storage and/or services in performing their functions, such as the embeddable widget generation techniques further discussed herein.

The embodiments disclosed herein recognize that conventional ways of sharing contents stored in the cloud would require either the users visiting a webpage interface (e.g., interface 104) or a client software user interface (e.g., interface 107) to access the contents. This may create an unpleasant user experience as the users may be required to leave or navigate away from the software applications (whether it is provided through the Internet, intranet, or other suitable sources) that they are currently using in order to gain the access, and/or the users may be required to install and execute a software or a plug-in that is foreign to their systems.

Accordingly, the present disclosure provides intuitive and easy ways to enable access to contents in the cloud-based platform within third-party applications 120, and especially when the third-party applications 120 are web-based (e.g., via a webpage), thereby improving user experience through better integration, alleviating workload for the administrators on tracking activities and maintaining data security, as well as reducing deployment time for the developers of the third-party applications 120 to integrate such functionalities.

More specifically, some embodiments of the host server 110 can utilize cross-platform computer languages (e.g., HyperText Markup Language (HTML) such as HTML5) to generate software codes which correspond to a software widget that enable access to contents in the cloud-based platform. The software widget may be embedded in a software product (e.g., a webpage, a web application or other suitable web-based services) so as to enable a user of the software product to access the contents without navigating away from the software product. For purposes of discussion herein, a “software widget” or a “widget” represents a type of computer software that typically comprises portable software codes capable of being executed in one or more different software platforms; therefore, it is noted that, although the present embodiments are particularly useful to implement web widgets that are included in webpages (e.g., that are HTML-based), the techniques disclosed herein can be similarly applied to other suitable kinds of widgets including, for example, a graphic user interface (GUI) widget, a desktop widget, a meta-widget, a widget application, and the like.

For example, the generated software codes, when included in a webpage provided by the third-party applications 120 and executed by a web browser on the user devices 102, can create an embedded widget within the webpage of the third-party applications 120 which provide select functionalities similar to those of the applications native to the cloud-based platform. The software widget can enable features including, for example, preview, file uploading (e.g., into repository 130), real time updates, editing, commenting and collaborator management. The disclosed techniques can allow customers, developers, as well as other partners of the developers to collaborate on centralized and synchronized contents, regardless of different location they may be in and different system they may employ. Additionally or alternatively, as the cloud-based platform adds more functionalities and/or collaboration features, the software widget can automatically receive these additional functions/features. For example, as the user adds new files to the folder (e.g., in the cloud-based platform) associated with a software widget, the new files can appear in the widget automatically.

In this way, among other benefits, the present embodiments can save time and increase productivity for the users by enabling them to access contents (e.g., files or folders) within the third-party applications 120 (e.g., embedded in an interface webpage of applications 120) that they are using, with requiring the users to navigate away or leave the applications 120. Further, the present embodiments can keep the accessed contents and discussions (e.g., comments, or highlights) centralized in the cloud-based platform. Still further, the present embodiments can allow administrators to keep the accessed contents centralized and secured in the cloud-based platform. The administrators can also select permission levels (e.g., for different instances of software widgets which may gain access to the same content), perform activity tracking/reporting, or adjust other suitable management and security options. Developers of the third-party applications 120 can now embed the software widget (e.g., as generated by the host server 110 using techniques disclosed herein) to any third-party applications (e.g., by including the generated HTML5 codes in their webpages) in a relatively short period of time, thus reducing the engineering workload when building an application base on the cloud-based platform.

More implementation details on the software code generation techniques which can be implemented on the host server 110 to render software widgets on webpages or other interfaces of third-party applications 120 are discussed in fuller detail below, and particularly with regard to FIG. 4.

FIG. 2 depicts an example diagram of a web-based/cloud-based or online collaboration platform deployed in an enterprise or other organizational setting 250 for organizing work items 215, 235, 255 and workspaces 205, 225, 245.

The web-based platform for collaborating on projects or jointly working on documents can be used by individual users and shared among collaborators. In addition, the collaboration platform can be deployed in an organized setting including but not limited to, a company (e.g., an enterprise setting), a department in a company, an academic institution, a department in an academic institution, a class or course setting, or any other types of organizations or organized setting.

When deployed in an organizational setting, multiple workspaces (e.g., workspace A, B C) can be created to support different projects or a variety of work flows. Each workspace can have its own associate work items. For example, workspace A 205 can be associated with work items 215, workspace B 225 can be associated with work items 235, and workspace N can be associated with work items 255. The work items 215, 235, and 255 can be unique to each workspace but need not be. For example, a particular word document can be associated with only one workspace (e.g., workspace A 205) or it can be associated with multiple workspaces (e.g., Workspace A 205 and workspace B 225, etc.).

In general, each workspace has a set of users or collaborators associated with it. For example, workspace A 205 is associated with multiple users or collaborators 206. In some instances, workspaces deployed in an enterprise can be department specific. For example, workspace B can be associated with department 210 and some users shown as example user A 208 and workspace N 245 can be associated with departments 212 and 216 and users shown as example user B 214.

Each user associated with a workspace can generally access the work items associated with the workspace. The level of access will depend on permissions associated with the specific workspace, and/or with a specific work item. Permissions can be set for the workspace or set individually on a per work item basis. For example, the creator of a workspace (e.g., one of user A 208 who creates workspace B) can set one permission setting applicable to all work items 235 for other associated users and/or users associated with the affiliate department 210, for example. Creator user A 208 can also set different permission settings for each work item, which can be the same for different users, or varying for different users.

In each workspace A, B . . . N, when an action is performed on a work item by a given user or any other activity is detected in the workspace, other users in the same workspace can be notified (e.g., in real time or in near real time, or not in real time). Activities which trigger real time notifications can include, by way of example but not limitation, adding, deleting, or modifying collaborators in the workspace, uploading, downloading, adding, deleting a work item in the workspace, creating a discussion topic in the workspace.

In some embodiments, items or content downloaded or edited can cause notifications to be generated. Such notifications can be sent to relevant users to notify them of actions surrounding a download, an edit, a change, a modification, a new file, a conflicting version, an upload of an edited or modified file.

In one embodiment, in a user interface to the web-based collaboration platform where notifications are presented, users can, via the same interface, create action items (e.g., tasks) and delegate the action items to other users including collaborators pertaining to a work item 215, for example. The collaborators 206 can be in the same workspace A 205 or the user can include a newly invited collaborator. Similarly, in the same user interface where discussion topics can be created in a workspace (e.g., workspace A, B or N, etc.), actionable events on work items can be created and/or delegated/assigned to other users such as collaborators of a given workspace 206 or other users. Through the same user interface, task status and updates from multiple users or collaborators can be indicated and reflected. In some instances, the users can perform the tasks (e.g., review or approve or reject, etc.) via the same user interface.

FIG. 3 depicts an example diagram of a workspace 302 in an online or web-based collaboration environment accessible by multiple collaborators 322 through various devices.

Each of users 316, 318, and 320 can individually use multiple different devices to access and/or manipulate work items 324 in the workspace 302 with which they are associated with. For example users 316, 318, 320 can be collaborators on a project to which work items 324 are relevant. Since the work items 324 are hosted by the collaboration environment (e.g., a cloud-based environment), each user can access the work items 324 anytime, and from any physical location using any device (e.g., including devices they own or any shared/public/loaner device).

Work items to be edited or viewed can be accessed from the workspace 302. Users can also be notified of access, edit, modification, and/or upload related-actions performed on work items 324 by other users or any other types of activities detected in the workspace 302. For example, if user 316 modifies a document, one or both of the other collaborators 318 and 320 can be notified of the modification in real time, or near real-time, or not in real time. The notifications can be sent through any of all of the devices associated with a given user, in various formats including, one or more of, email, SMS, or via a pop-up window in a user interface in which the user uses to access the collaboration platform. In the event of multiple notifications, each notification can be depicted preferentially (e.g., ordering in the user interface) based on user preferences and/or relevance to the user (e.g., implicit or explicit).

For example, a notification of a download, access, read, write, edit, or uploaded related activities can be presented in a feed stream among other notifications through a user interface on the user device according to relevancy to the user determined based on current or recent activity of the user in the web-based collaboration environment.

In one embodiment, the notification feed stream further enables users to create or generate actionable events (e.g., as task) which are or can be performed by other users 316 or collaborators 322 (e.g., including admin users or other users not in the same workspace), either in the same workspace 302 or in some other workspace. The actionable events such as tasks can also be assigned or delegated to other users via the same user interface.

For example, a given notification regarding a work item 324 can be associated with user interface features allowing a user 316 to assign a task related to the work item 324 (e.g., to another user 316, admin user 318, creator user 320 or another user). In one embodiment, a commenting user interface or a comment action associated with a notification can be used in conjunction with user interface features to enable task assignment, delegation, and/or management of the relevant work item or work items in the relevant workspaces, in the same user interface.

FIG. 4 depicts a block diagram illustrating an example of components in a host server 400 (e.g., server 110, FIG. 1) with capabilities that that generate embeddable widgets capable of accessing contents in a cloud-based platform. The widget can be embedded in, for example, a webpage rendered by a browser (e.g., running on devices 102), or an application operating on a mobile device 102. With additional reference to FIGS. 1-3, the software widget generation techniques which the host server 400 can employ are described. The cloud-based platform can be shared between a vendor user 316 (FIG. 3) and collaborators 322 (FIG. 3) of the user 316.

The host server 400 of the web-based or online collaboration environment can generally be a cloud-based service. The host server 400 can include, for example, a network interface 410, a widget generation engine 420 having a configuration parameter module 430 and a source code generator module 435, and a content access controller 440. In some embodiments of the host server 400, the configuration parameter module 430 further includes a layout customization module 432 a, a function customization module 432 b, and a permission control module 432 c. One or more embodiments of the content access controller 440 can include, for example, a download module 442 and an upload controller 444.

As used herein, a “module,” “a manager,” an “interface,” or an “engine” includes a general purpose, dedicated or shared processor and, typically, firmware or software modules that are executed by the processor. Depending upon implementation-specific or other considerations, the module, manager, interface, or engine can be centralized or its functionality distributed. The module, manager, interface, or engine can include general or special purpose hardware, firmware, or software embodied in a computer-readable (storage) medium for execution by the processor. As used herein, a computer-readable medium or computer-readable storage medium is intended to include all media that are statutory (e.g., in the United States, under 35 U.S.C. §101), and to specifically exclude all media that are non-statutory in nature to the extent that the exclusion is necessary for a claim that includes the computer-readable (storage) medium to be valid. Known statutory computer-readable mediums include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware.

The network interface 410 can be a networking module that enables the host server 400 to mediate data in a network with an entity that is external to the host server 400, through any known and/or convenient communications protocol supported by the host and the external entity. The network interface 410 can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G, LTE, etc.), Bluetooth, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater.

As previously described, overall, the host server 400 can generate (e.g., in response to an embedding request) software codes which correspond to a software widget that enable access to contents in the cloud-based platform.

More specifically, in some embodiments, the host server 400 can receive (e.g., via the network interface 410) an embedding request identifying a target content (e.g., a work item 324, FIG. 3, such as a file or a folder) in the cloud-based platform (e.g., workspace 302, FIG. 3). Afterwards, the widget generation engine 420 of the host server 400 can automatically generate (e.g., via the source code generator module 435) a plurality of software codes which correspond to a software widget that enables access to the target content. In one or more embodiments, the software widget may be embedded in a third-party software product (e.g., a webpage, a web application or other suitable web-based services, such as third-party applications 120, FIG. 1) so as to enable a customer user of the software product to access the contents without leaving or navigating away from the software product. In other words, the customer user can access the target content simply by using the interface (e.g., in forms of webpages) provided by the third-party software product, without the need of leaving the software product and without the need of using native cloud-based platform interfaces such as interfaces 104 and 107 (FIG. 1) in order to gain the access. The vendors of the third-party applications 120 can also enjoy better control over the contents to which the customer user has access.

In some embodiments, to utilize the host server 400's widget generation functionalities, the embedding request can be received from a user (e.g., a vendor of the third-party applications 120) by using widget generation interfaces provided by the host server 400 in, for example, interfaces 104. FIGS. 5A-5C respectively depict screenshots showing example user interfaces 500, 502, and 504 which are embodiments of the widget generation interfaces for generating embeddable widgets capable of accessing a file in a cloud-based platform.

As illustrated in FIG. 5A, a widget generation interface 500 (e.g., which is displayed in the web browser of the users device 102) can be operated by the user in generating software codes that correspond to software widgets. In some embodiments, the generated software codes corresponding to the widgets can be executed, for example, in a web browser of user devices (e.g., devices 102, FIG. 1). In one or more embodiments, the software codes can be executed by the web browser natively (e.g., so that a plug-in is not required). An example type of the software codes is HTML5. As such, the software codes are configured to be directly included in a software product (e.g., by copying the HTML5 code into the webpage of the third-party applications 120) without a compilation process. According to some embodiments, the generated software codes can be used to embed a software widget that accesses target contents into the third-party vendor user's website or blog. Some examples of the access to the target content can include viewing the contents of a file, whereas the widget can be an embedded reader that shows pages of a document file, an embedded image viewer that shows images from a photo file, or an embedded media player that plays music in an audio file or video frames from a video file, etc.

More specifically, to embed a file in a webpage, the user can first locate the file in the cloud-based platform or in workspace 302 using the interface 500 (e.g., interface 104). The interface 500 includes a menu button (e.g., button 510), and the user can generate the embedding request by choosing to activate the “Embed file in your site” function from a “Share” submenu under the menu. The host server 400 receives this request, and can generate another widget generation interface (e.g., a pop-up window such as interface 502 of FIG. 5B) where the user can adjust or enter configuration parameters to customize the embeddable widget. The adjustments of configuration parameters can be received by the configuration parameter module 430, and the source code (e.g., HTML5) generator module 435 can generate and/or adjust the embeddable computer code accordingly. The resulting computer code can be presented to the user via the user interface 502 (e.g., in area 520, as shown in FIG. 5B).

According to some specific examples, the customization can includes layout definitions for the software widget, such as size, height, width, or color theme of the widget. The layout definitions can be received by the layout customization module 432 a for processing (e.g., for code generating in the code generator module 435). As illustrated in the example of FIG. 5B, the user can change the size of the embedded widget by adjusting the pixel numbers next to “Width” and “Height” as well as change the background color of the software widget.

Additionally or alternatively, the customization can include adjustment of functionalities of the software widget in accessing the target content, such as adjusting permission levels, or different tool functionalities like print, write, edit and save back, share link, download access, copy and paste, etc. Additional functionalities that can be adjusted can include editing the file, commenting on the file, highlighting portions of the file, or sharing the file. The adjustment can be received by the function customization module 432 b and/or the permission control module 432 c for processing (e.g., for code generating in the code generator module 435). As illustrated in the example of FIG. 5B, the user can select the amount of access to the document the user wishes the user's customers to have by adjusting the check boxes on the right side of the interface 502. In this particular case, the user can turn off the ability to print the document, turn off the ability to download the document, as well as disable the customer users from sharing a link to the file.

Further, in some embodiments, the widget generation engine 420 can prompt the user with an option to preview the software widget, and upon activation of the option, the host server 400 can cause a web browser of the user to execute the software codes so as to generate the software widget in, for example, a new webpage. In the example illustrated in FIG. 5B, the user can preview the customized embeddable widget by choosing a ‘Preview this embed’ function 530, and a new interface can be displayed (e.g., as a pop-up window, as a new webpage, or the like) to show an actual software widget as populated by the web browser based on the generated computer code. Such preview of the actual software widget is shown in widget preview interface 504 of FIG. 5C. In this way, the vendor user can verify the software widget's functionalities, layout, and in some embodiments, different permission settings.

The widget generation engine 420 can prompt the user to copy the software codes into a memory on a device of the user. For the example shown in FIG. 5B, the vendor user can choose a “Copy to Clipboard” function 540 to copy the computer code (e.g., in forms of HTML) to a clipboard (e.g., a temporary cache memory) of the user's device. As such, after the user becomes satisfied with the look and feel of the software widget, the user can copy and paste the computer codes into a location (e.g., a webpage) of the vendor's own desire that allows custom HTML widget to be embedded.

It is noted that, in some embodiments, the software codes are uniquely generated by the source code generator module 435 so that different software widgets generated in a plurality of instances can access the identified target content and each have a distinct configuration. In some of these embodiments, each time the vendor user activates the “Embed file in your site” option, a unique instance of the widget can be created. This technique can allow the vendor user to create multiple embedded instances of the same target content (e.g., a single document), and each embedded instance of software widget can have its own custom access and size settings. In an additional or alternative embodiment, the vendor user can change the settings of an existing embedded widget by generating a new widget for the file or content with the settings the user so desires, and replace the old computer codes included in the user's computer product (e.g., a website).

Some examples of file types that the software widgets can view include Adobe Acrobat (.pdf), Adobe Illustrator (.ai), Adobe Photoshop (.psd), CSV, HTML, Microsoft Excel (.xls, .xlsx), Microsoft Powerpoint (.ppt, .pptx), Microsoft Word (.doc, .docx), Open Office Presentation (.odp), Open Office Spreadsheet (.ods), Open Office Word Processing (.odt), RTF, TXT, Word Perfect (.wpd), JPEG, PNG, GIF, TIFF, BMP, FLV, SWF, MP3, and so forth. In some embodiments, if the target content (e.g., file) is either not a supported file type, or if the vendor user do not have sufficient privileges to share that file, the widget generation engine 420 does not display the option to embed the file to the user.

Furthermore, some other examples of the access to the target content can include viewing the contents of a folder, whereas the widget can be an embedded file manager that shows lists of files in the folder as well as a select number of other functions (as controlled by configuration parameter module 430) that a typical file manager can have. FIG. 6A-6C respectively depict screenshots showing example user interfaces 600, 602, and 604 for generating embeddable widgets capable of accessing a folder in a cloud-based platform.

More specifically, in addition or as an alternative to the aforementioned functionalities (e.g., with respect to embedding one or more individual files) of the widget generation engine 420, the vendor user can choose embed a folder of the cloud-based platform in, for example, a website that supports HTML embed code.

In manners similar to the embodiments mentioned above, in some embodiments, the vendor user can first generate an embedding request to utilize the host server 400's widget generation functionalities. As illustrated in FIG. 6A, a widget generation interface 600 (e.g., which can be displayed in the web browser of the users device 102) can be operated by the user to generate the request. In the example shown in FIG. 6A, the user can click on a “Folder Options” function 610 in the interface 600, select “Share,” and select “Embed Folder in Your Site” to generate the embedding request to the host server 400.

The host server 400 receives (e.g., via the network interface 410) this request, and can generate another widget generation interface (e.g., a pop-up window such as interface 602 of FIG. 6B) where the user can adjust or enter configuration parameters to customize the layout and the functionalities of the embeddable widget. More specifically, similar layout parameters (e.g., size, color, etc.) that are discussed above for software widgets that access a file can be applicable (e.g., by the layout customization module 432 a) to the software widgets that access a folder. With regard to functionality, in addition to displaying a list files in the folder, examples of functionalities that the user can adjust for the software widget that accesses the target folder can include enabling downloading a number of files from the folder, changing a sorting option (e.g., by name, size, type, date, tag, etc.) for the files in the folder, or changing a different view style (e.g., list, thumbnail, details, etc). The adjustment of functionalities can be received by the function customization module 432 b and/or the permission control module 432 c. As mentioned, the source code generator module 435 generates computer codes based on the configuration parameters, and the widget generation engine 420 displays the generated computer codes in an interface (e.g., area 620 of interface 602).

In some embodiments, the user can also preview the embedded folder by selecting a “Preview this embed” function, an example of which is illustrated as function 630. An example showing the “preview” of the software widget that can access a folder is shown in interface 604 of FIG. 6C. When the user finishes customizing, the user can select a “Copy to Clipboard” function 640 to copy the generated computer codes, and paste the computer codes (e.g., HTML) in a desired location.

Additional or alternatively, the user can still edit an existing folder widget after it has been embedded. In some embodiments, to edit an existing embedded folder, the vendor user is required by the host server 400 to log into his or her account first.

Still further, in some embodiments, the access to the target content includes uploading a file to the folder so that the user can accept files by using the software widget. For example, the user can set up a folder in the cloud-based platform for other companies to submit bids for business, or the user may want to accept submissions for a writing contest. Accordingly, the widget generation engine 420 can create a software widget with access to a folder and allowing people to upload files directly to the user's shared folder.

In one or more embodiments, The user can first create a folder in the cloud-based platform for people to upload files, or alternatively, can choose an existing folder. Although not shown for simplicity, in the customization interface 602, one of the configuration parameters can be allowing upload. Other appropriate settings such as permission level, or security handling (e.g., whether to scan and/or quarantine a uploaded file) can also be adjusted. The function customization module 432 b and the permission control module 432 c receive these settings, and the source code generator module 435 generates the computer codes based on all the selected/adjusted configuration parameters. After including (e.g., by copying and pasting) the code into the user's computer product (e.g., the vendor's website), the folder can receive files from the user's customers. As new files and folders are uploaded, they can appear in the user's folder for review.

In some embodiments, the host server 400 can inspect the uploaded files including, for example, scanning for virus, Trojan horses, or other unwanted information. Further, one or more embodiments of the host server 400 can quarantine, submit to the user for review, or perform other actions on the uploaded file in response to a result from the inspecting.

Also, upon a widget being used to access contents in the workspace 302, the content access controller 440 in the host server 400 can ensure that no unauthorized access can be performed by the software widget. In one example, the download module 442 of the access controller 440 can track what activities are performed on the target content at what time and by which performer. One or more embodiments provide that the access controller 440 can keep track of different versions of the accessed content. Additionally, the access controller 440 may generate reports of the monitoring to an administrator of the system for review.

Moreover, in some embodiments, the upload module 444 of the content access controller 440 can prevent another software widget from accessing the uploaded file. Additionally, some embodiments of the upload module 444 can prevent a software widget from accessing (e.g., viewing) files other than the ones that are uploaded by the software widget itself. In this way, the customers of the user can only upload files, but are not be able to view or access other contents of the folder through the software widget.

FIG. 7 depicts a flowchart illustrating an example process 700 for generating embeddable widgets capable of accessing contents (e.g., a folder, a file, or other suitable work items 324, FIG. 3) in a cloud-based platform (e.g., workspace 302, FIG. 3). The method 700 is performed, for example, in a host server of the workspace 302 (e.g., server 400, FIG. 4).

First, the host server 400 can receive (710) (e.g., via the network interface 410, FIG. 4) an embedding request identifying a work item 324 in the workspace 302. Afterwards, the host server 400 can automatically generate (720) (e.g., via the source code generator module 435, FIG. 4) a plurality of software codes which correspond to a software widget that enables access to the target content.

In one or more embodiments, the software widget can be embedded (722) in a third-party software product such as a webpage, a web application or other suitable web-based services so as to enable a customer user of the webpage to access the work item 324 without leaving or navigating away from the webpage. In other words, the host server 400 enables the customer user to access the work item 324 by using the webpage (e.g., as provided by a third-party vendor) without the need of leaving the webpage.

Further, in some embodiments, the software codes are uniquely generated (724) by the host server 400 (e.g., using source code generator module 435, FIG. 4) so that different software widgets generated in a plurality of instances can access the same work item 324, and each instance of software widget can have a distinct configuration. In some of these embodiments, each time the vendor user sends an embedding request to the host server 400, a unique instance of the widget can be created by the host server 400. This technique can allow the vendor user to create multiple embedded instances of the same target content (e.g., a single document), and each embedded instance of software widget can have its own custom access and size settings.

In an additional or alternative embodiment, the vendor user can change the settings of an existing embedded widget by generating a new widget for the file or content with the settings the user so desires, and replace the old computer codes included in the user's computer product (e.g., a website).

FIG. 8 shows a diagrammatic representation 800 of a machine in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, can be executed.

In alternative embodiments, the machine operates as a standalone device or can be connected (e.g., networked) to other machines. In a networked deployment, the machine can operate in the capacity of a server or a client machine in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.

The machine can be a server computer, a client computer, a personal computer (PC), a user device, a tablet, a phablet, a laptop computer, a set-top box (STB), a personal digital assistant (PDA), a thin-client device, a cellular telephone, an iPhone, an iPad, a Blackberry, a processor, a telephone, a web appliance, a network router, switch or bridge, a console, a hand-held console, a (hand-held) gaming device, a music player, any portable, mobile, hand-held device, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.

While the machine-readable medium or machine-readable storage medium is shown in an exemplary embodiment to be a single medium, the term “machine-readable medium” and “machine-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” and “machine-readable storage medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the presently disclosed technique and innovation.

In general, the routines executed to implement the embodiments of the disclosure, can be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as “computer programs.” The computer programs typically comprise one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processing units or processors in a computer, cause the computer to perform operations to execute elements involving the various aspects of the disclosure.

Moreover, while embodiments have been described in the context of fully functioning computers and computer systems, those skilled in the art will appreciate that the various embodiments are capable of being distributed as a program product in a variety of forms, and that the disclosure applies equally regardless of the particular type of machine or computer-readable media used to actually effect the distribution.

Further examples of machine-readable storage media, machine-readable media, or computer-readable (storage) media include, but are not limited to, recordable type media such as volatile and non-volatile memory devices, floppy and other removable disks, hard disk drives, optical disks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks, (DVDs), etc.), among others, and transmission type media such as digital and analog communication links.

The network interface device enables the machine 2800 to mediate data in a network with an entity that is external to the host server, through any known and/or convenient communications protocol supported by the host and the external entity. The network interface device can include one or more of a network adaptor card, a wireless network interface card, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater.

The network interface device can include a firewall which can, in some embodiments, govern and/or manage permission to access/proxy data in a computer network, and track varying levels of trust between different machines and/or applications. The firewall can be any number of modules having any combination of hardware and/or software components able to enforce a predetermined set of access rights between a particular set of machines and applications, machines and machines, and/or applications and applications, for example, to regulate the flow of traffic and resource sharing between these varying entities. The firewall can additionally manage and/or have access to an access control list which details permissions including for example, the access and operation rights of an object by an individual, a machine, and/or an application, and the circumstances under which the permission rights stand.

Other network security functions can be performed or included in the functions of the firewall, can be, for example, but are not limited to, intrusion-prevention, intrusion detection, next-generation firewall, personal firewall, etc. without deviating from the novel art of this disclosure.

Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to.” As used herein, the terms “connected,” “coupled,” or any variant thereof, means any connection or coupling, either direct or indirect, between two or more elements; the coupling of connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, shall refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number can also include the plural or singular number respectively. The word “or,” in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.

The above detailed description of embodiments of the disclosure is not intended to be exhaustive or to limit the teachings to the precise form disclosed above. While specific embodiments of, and examples for, the disclosure are described above for illustrative purposes, various equivalent modifications are possible within the scope of the disclosure, as those skilled in the relevant art will recognize. For example, while processes or blocks are presented in a given order, alternative embodiments can perform routines having steps, or employ systems having blocks, in a different order, and some processes or blocks can be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or subcombinations. Each of these processes or blocks can be implemented in a variety of different ways. Also, while processes or blocks are at times shown as being performed in series, these processes or blocks can instead be performed in parallel, or can be performed at different times. Further, any specific numbers noted herein are only examples: alternative implementations can employ differing values or ranges.

The teachings of the disclosure provided herein can be applied to other systems, not necessarily the system described above. The elements and acts of the various embodiments described above can be combined to provide further embodiments.

Any patents and applications and other references noted above, including any that can be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the disclosure can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further embodiments of the disclosure.

These and other changes can be made to the disclosure in light of the above Detailed Description. While the above description describes certain embodiments of the disclosure, and describes the best mode contemplated, no matter how detailed the above appears in text, the teachings can be practiced in many ways. Details of the system can vary considerably in its implementation details, while still being encompassed by the subject matter disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the disclosure should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the disclosure with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the disclosure to the specific embodiments disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the disclosure encompasses not only the disclosed embodiments, but also all equivalent ways of practicing or implementing the disclosure under the claims.

While certain aspects of the disclosure are presented below in certain claim forms, the inventors contemplate the various aspects of the disclosure in any number of claim forms. For example, while only one aspect of the disclosure is recited as a means-plus-function claim under 35 U.S.C. §112, ¶ 6, other aspects can likewise be embodied as a means-plus-function claim, or in other forms, such as being embodied in a computer-readable medium. (Any claim intended to be treated under 35 U.S.C. §112, ¶ 6 begins with the words “means for”.) Accordingly, the applicant reserves the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the disclosure. 

What is claimed is:
 1. A method for enabling access a cloud-based platform, the method comprising: receiving a request identifying a target content in the cloud-based platform; and automatically generating a plurality of software codes which correspond to a software widget that enables access to the target content.
 2. The method of claim 1, wherein the software widget is to be embedded in a software product so as to enable a user of the software product to access the target content without navigating away from the software product.
 3. The method of claim 1, wherein each software widget is generated as a unique instance.
 4. The method of claim 1, wherein the software codes are uniquely generated so that different software widgets generated in a plurality of instances can access the identified target content and each have a distinct configuration.
 5. The method of claim 1, further comprising: prompting a user to preview the software widget, wherein activation of the preview causes a web browser of the user to execute the software codes.
 6. The method of claim 1, further comprising: prompting a user to copy the software codes into a memory on a device of the user.
 7. The method of claim 1, wherein the software codes are configured to be directly included in a software product without a compilation process.
 8. The method of claim 7, wherein the software product is a webpage or a web application.
 9. The method of claim 1, wherein the request is received from a user, the method further comprising: presenting, via a user interface, the plurality of software codes to the user.
 10. The method of claim 1, wherein the target content comprises a file, and wherein the access to the target content includes viewing the file.
 11. The method of claim 10, wherein the access to the target content further includes one or more of: editing the file, commenting on the file, highlighting portions of the file, or sharing the file.
 12. The method of claim 1, wherein the target content comprises a folder, and wherein the access to the target content includes displaying a list of work items in the folder.
 13. The method of claim 12, wherein the access to the target content further includes one or more of: downloading a number of work items from the folder, changing a sorting option for the work items in the folder, or changing a different view style.
 14. The method of claim 1, wherein the target content comprises a folder, and wherein the access to the target content includes uploading a file to the folder.
 15. The method of claim 14, further comprising: inspecting the uploaded file; and performing actions on the uploaded file in response to a result from the inspecting.
 16. The method of claim 14, further comprising: preventing another software widget from accessing the uploaded file.
 17. The method of claim 1, further comprising: receiving configuration parameters to customize the software widget.
 18. The method of claim 17, wherein the customization includes layout definitions for the software widget.
 19. The method of claim 17, wherein the customization includes adjustment of functionalities of the software widget in accessing the target content.
 20. The method of claim 1, further comprising: tracking access activities performed via each software widget to the target content.
 21. The method of claim 1, wherein the cloud-based platform is shared between a user and collaborators of the user.
 22. A computer server which hosts a cloud-based environment shared among a user and collaborators of the user, the server comprising: a processor; and a memory unit having instructions stored thereon which when executed by the processor, causes the processor to: receive a request identifying a target content in the cloud-based platform; and automatically generate a plurality of software codes which correspond to a software widget that enables access to the target content.
 23. The server of claim 22, wherein the software widget is to be embedded in a software product so as to enable a user of the software product to access the target content without navigating away from the software product.
 24. The server of claim 22, wherein each software widget is generated as a unique instance.
 25. The server of claim 22, wherein the software codes are uniquely generated so that different software widgets generated in a plurality of instances can access the identified target content and each have a distinct configuration.
 26. The server of claim 22, wherein the processor is further configured to: prompt a user to preview the software widget, wherein activation of the preview causes a web browser of the user to execute the software codes.
 27. The server of claim 22, wherein the processor is further configured to: prompt a user to copy the software codes into a memory on a device of the user.
 28. The server of claim 22, wherein the software codes are configured to be directly included in a software product without a compilation process.
 29. The server of claim 28, wherein the software product is a webpage or a web application.
 30. The server of claim 22, wherein the request is received from a user, and wherein the processor is further configured to: present, via a user interface, the plurality of software codes to the user.
 31. The server of claim 22, wherein the target content comprises a file, and wherein the access to the target content includes one or more of: viewing the file, editing the file, commenting on the file, highlighting portions of the file, or sharing the file.
 32. The server of claim 22, wherein the target content comprises a folder, and wherein the access to the target content includes one or more of: displaying a list of work items in the folder, downloading a number of work items from the folder, changing a sorting option for the work items in the folder, or changing a different view style.
 33. The server of claim 22, wherein the target content comprises a folder, and wherein the access to the target content includes uploading a file to the folder.
 34. The server of claim 33, wherein the processor is further configured to: inspect the uploaded file; and perform actions on the uploaded file in response to a result from the inspecting.
 35. The method of claim 33, wherein the processor is further configured to: prevent another software widget from accessing the uploaded file.
 36. The server of claim 33, wherein the processor is further configured to: receive configuration parameters to customize the software widget.
 37. The server of claim 36, wherein the customization includes layout definitions for the software widget.
 38. The server of claim 36, wherein the customization includes adjustment of functionalities of the software widget in accessing the target content.
 39. The server of claim 22, wherein the processor is further configured to: track access activities performed via each software widget to the target content.
 40. A machine-readable storage medium having stored thereon instructions which, when executed by a processor on a server, cause the processor to: receive a request identifying a target content in a cloud-based platform shared among a user and collaborators of the user; and automatically generate a plurality of software codes which correspond to a software widget that enables access to the target content, wherein the software widget is to be embedded in a software product so as to enable a user of the software product to access the target content without navigating away from the software product, and wherein each software widget is generated as a unique instance.
 41. A system which hosts a cloud-based environment shared among a user and collaborators of the user, comprising: means for receiving a request identifying a target content in the cloud-based platform; and means for automatically generating a plurality of software codes which correspond to a software widget that enables access to the target content, wherein the software codes are uniquely generated so that different software widgets generated in a plurality of instances can access the identified target content and each have a distinct configuration. 